Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
🚀 New features to boost your workflow:
|
|
This is technically breaking, as reported by the semver check, but nobody would be using the removed type because it's useless / not referenced anywhere. |
This one needs to be public in order for users to implement
Ugh, thank you. Sorry I left that in. |
Ah, interesting, but do we expect users to implement |
|
I dont necessarily expect it - I doubt anyone is implementing |
|
You know what, you're completely right. I lost track of what those traits were for, it does make sense that people can use I'll update this PR and remove that change. Thanks! |
So YAML's integer based maps were what I had in mind when I created it. I didn't look to see whether or not serde_yaml supported the structure but figured if a crate ever came along that did, they'd need their own error. In retrospect, it was likely overkill and have made the errors themselves a bigger pain than needed. |
|
Since you haven't explicitly nacked, and other than the deprecation this is mostly docs changes, I'm going to proceed with merging. 👍 |
I changed my mind on removing serde as a default feature. It is a heavy dependency to bring by default, but it's easy enough to disable the default features, and I do see the "common" use case for jsonptr involving
serde_json. Also I guessDiagnosemakes sense when you consider that the error it converts isn't yet aReport, even though it implementsDiagnostic. Perhaps it'sDiagnosticthat requires reconsidering.Changes I'm pushing forward:
diagnostic::Label::newprivatevalidate_bytesNoLeadingSlashstructdelete.rsdocsResolveErrorLeft for standalone PRs:
index::ParseIndexErrorandtoken::EncodingErrorto the new error system.Diagnose